seewhat.gif (682 bytes)
 
Interest
Photo Album
Favorites

Wheretoday.gif (22610 bytes)

Mailing List

Stick a note or something on our Bulletin Board

Check out my list of search engines

MPEG Layer

Contact InFo 

Page agreement 

join2.gif (2642 bytes)

frontpag.gif (9866 bytes)

IRC War Tactics & Principles

Basic War 

OVERVIEW: This section is meant for those of you new to IRC war. It will teach  
you the basics of flooding, and nick colliding. It also includes many tips  
that you should follow. 

1. Flooding 

    This is a somewhat old fashiond, but effictive way to get rid of  
    people you hate. What flooding does is, cause a person to send so much    information to a server, that it disconnects them. This is  
    accomplised by loading clones. Clones are more connections to a  
    server and often made by copying the IRC client numerous times. Then 
    using a flood script, it tells the clones to simultaniously send  
    massive amounts of information to a person. When there client tries 
    to process this all of it, it sends too much information to a server 
    and kills them.  

    There are many floods out there and choosing the correct one is  
    important. Good ones are DCC and CTCP floods. Ones that dont do shit 
    are Text Floods, Notice floods and invite floods. As well as crap  
    floods that dont do anything but look mean. Another factor is the  
    number of clones to use. To flood a single person, the best bet would 
    be a 3 clone CTCP flood such as a CLIENTINFO, USERINFO, or VERSION. 
    ECHO floods are extemely powerfull, but require more clones. DCC  
    floods are also effective. There are 4 different kind of DCC floods. 
    The DCC Chat flood, send many DCC chat windows to a person. DCC 
    Send floods, sends a ton of DCC send requests. And if the DCC's are  
    accepted it can fill there hardrive with some crappy files. DCC  
    Resume and Accept are the 2 other kinds. These were once the best  
    floods available, but no IRC clients support them anymore so they are 
    futile.  

    When cloning/flooding you have to be carefull not to get caught. It  
    often means a K-line. To keep this from happening remember these  
    tips. Don't clone unless its absolutely necessary, why risk it? Kill 
    your clones after the flood is over, you want them dead right away. 
    Use nick changing clones for flooding people. Most people know that 
    you can do a /whois to see the person, but most don't know about  
    /whowas. So if the clone changes nicks after the flood, they wont  
    find who did it. NEVER flood channels with IRCops or Network admins! 
    That will mean a sure K-line. Also if it is entirely possible, flood  
    with a friend, the less clones at a site the less chance you have of  
    getting cought. 

2. Nick Colliding. 

    Nick colliding is when 2 people have the same nicks. Servers can't  
    have this because it would be screwing a lot up. So one of the people  
    must die. There are 2 methods of nick collision. Split server  
    colliding and lag colliding. Split server colliding is when you put 
    a bot onto a split server with the persons nick you want killed. On 
    a netmerge, it kills them both. This method does not work on  
    undernet. The other method is called Lag colliding. this can only be 
    done when a person changes nicks. What it does is this. 1. Lamer  
    changes his nick. 2. Script sees this and sends a signal to a collide 
    bot on a laged server. 3. In a few seconds when the lag catched up, 
    the server that the collide bot is on kills the other person because 
    it thinks that the person on its server had the nick first. This isnt 
    A very good method to use on a takeover, but it is fun to sit in a  
    large channel and watch people being collided. 

  

                CHANNEL TAKING 

OVERVIEW: Taking over channels is a great way to show your power and to get 
revenge on your enemy. Channel taking is basically what IRC war is about,  
control of territory. This section contains lots of usefull ways to do that. 

1. Channel Flooding: 
  
This method is fun, but the hard part is more and more people are  
    unfloodable. But if you can flood out all the people, the rest is  
    easy. Get all the clones out and then rejoin the channel and have  
    ops. However if an enemy gets back in before you can pull out this  
poses a dilema. An opless channel with 2 people wanting it. What do  
    you do? Ride a netsplit!  

2. Riding a Netsplit: 

    On an opless channel it is easy to regain ops on a netsplit. What you 
    do is this. On the event of a split get on the split server. What  
    you should see is about nothing, there won't be many channels people. 
    So join a channel like normal and if no one else is there you will  
    have ops. Then wait for a netmerge, and when its all merged, you will 
    be a lone op leaving you to do what you want! 

    Doing this on a channel which already has ops isn't as easy. On  
    Undernet it is IMPOSSIBLE. But that doesnt mean you can't have fun :) 
    Get ops and wait for a netmerge. Then as its starting to merge run 
    a desync. What this does is fill banlists, empty banlists and change 
    channel modes. This really fucks up already fucked up servers. They 
    are already trying to get the channels set back to normal, but this 
    causes more modes and will lag a channel to death. It also fucks up 
    non-split bots. It can even cause them to flood off or crash. So  
    although you can't hack ops you can get definate revenge. It can  
    leave a channel with server modes screwing it up for a half hour 
    sometimes. 

    If you are actually lucky enough to be on a lame network that  
    doesn't have anti-nethack code, you can take over a channel on a  
    netsplit with the proper script. 1. You need netsplit protection.  
    This will deop when the server tries to op the person. 2. Also a good  
    way to do it is by having a mode that kickbans each person on a  
    netmerge join. This combined with the netsplit protection will leave  
    you the channel after only a slight battle. 

3. Asking for ops. 

    This is the easiest way to takeover a channel. It is effective and it 
    is legal, meaning if they op you and you massdeop them, the IRCops  
    can't do anything about it. The best way to get ops is to sit in a  
    channel for a little while being helpfull and nice (the hard part). 
    Then say "hey, you think you can op me? I am trustable. I have been  
    helping you since I got here" This is where a script that allows you 
    to massdeop everyone is handy. What this mode will do is as soon as 
    you are oped, it performs a mass deop, 6 people at a time on everyone  
    but yourself. They won't know what hit them! Another way is to wait 
    a minute after they op you then run a massdeop that does the same  
    thing. After your alone with ops you can do whatever ya want, lock it 
    up, kick everyone, ban everyone what ever you feel like doing with  
    your new channel.  
 

                Advanced War 

OVERVIEW: Although war scripts are becoming more advanced all the time, the 
server and IRCops are getting better as well. Many servers now incorperate 
clone detection. This goes through lists of people, matching IP's and then  
notifies IRCops. This can keep you from cloning enough to decently flood  
somone. Many servers code now have anti netsplit takeover features. This can 
stop you from hacking ops using a netsplit. Only allowin you to ride into an  
opless channel. Anti Collide is also used on may servers. It times when the  
person changes nicks and kills the newest one (usually your bot). So now if  
somone fucks with you your not gonna be a pussy and not do anything about it 
just because you can't clone and shit?? FUCK NO! 

1. Nuking 

    Nuking is a great way to get somone off IRC fast! How it works is  
    this. A nuke program sends information over the persons IRC server 
    and then after it hits them, it will cause errors suck as dead  
    Socket, connection refused, eof from client, and machine is not on  
    the network.  

    To nuke somone you first need a fast modem, 28.8 or better. You also  
    need TrumpetŠ Winsock. This is a dial up program that will  
    communicate very fast with the modem. It is readilly available on the 
    web. Then after you got those essentials, you need a Nuke program. 
    I would recommend Winuke4 by CHAOS INC. or Wnewk for windows  
    machines. Or if you are on a mac, MAC NUKE.  

    Once you get the programs up and running, it is very easy to get  
    revenge, takeover channels, and kill people quickly. 

2. ICMP Bombs. 

    ICMP is an extremely powerfull way to screw up not only the persons  
    IRC session, but their entire connection to the Internet. How it  
    works is this way, it sends ICMP messages, at an extremely fast rate, 
    causing severe line noise, and modem lag. It will cause so much lag, 
    that it will ping somone off an IRC server. 

    To ICMP you need a Unix Shell account. Why you ask? Because to ICMP 
    effectivly you need more than any dial up modem can give you. You  
    need atleast a T1 shell. There are many Windows ICMP bombers  
    available, but they dont work very well. Its the speed that matters. 

    Here are two formats to ICMP off a Unix shell: 

    ping -s <ip address> <packet size> <# of packets> 
    ping -s (packet size) -c (# of packets) <-f> (ip address) 
  
    <IP address> is the *!*@what.ever.this.is 
    <packet size> is the Size of each packet to send, try 30k size, and  
    <# of packets> is how many to send 3000 is a good # 
    -f is optional in the second, and blasts the packets out at at 20/sec 

3. Botnet/Floodnet 

    Because it is hard to clone without getting caught, you need a way 
    to flood somone, without setting off clone detectors. How do you do  
    this? Floodnet. There are two different ways to Floodnet. 1 is with  
    Eggdrop bots, these "botnets" are consisted of many eggdrops all linked 
    together and having a common flood script. There has been botnets  
    with many hundreds linked. It is very hard to stop floods from them. 
    Another way is now being used by individual scripts. The scripts  
    contain common commands, and allow users with the same script to link 
    together by DCC and combine clones. There are advantages and  
    disadvantages to both. Advantages of botnets is that they are always 
    online because they are on Shells. But the disadvantages are that 
    there aren't dynamic like a clone floodnet.  

  Lightbulb.gif (6734 bytes)           Click here to return to my Homepage